Changes/fixes in Release v1.3.2
--Added Windows Server 2016 to list of valid OS versions
--InstallSCOMCert now installs the the XXXRack-SubCA into the Intermediate cert store instead of the Trusted Root store
--SCOM 2012 R2 Agent is UR11 KB3183990 

Changes/fixes in Release v1.3.1
--Updated the InstallSCOMCert utility to use a keylength of 2048 by default
--added additional "datacenters" for testing, Internal Segment Support, and Dedicated Exchange
--updated the Help link to point to the One Wiki article
--Added OMv3.1CertCheck.ps1 for extended Cert checks if needed
--PortQry.exe is packaged
--SCOM 2012 R2 Agent is ur7 KB3064919
--Packaged in SFX for Rackspace SCOM Installer

Changes/fixes in Release v1.3.0
--removed support for SCOM 2007 agent
--upgraded agent to SCOM 2012 R2 agent
--changed the RemoveAgent method to remove the agent via WMI; removes the agent regardless of the version being installed and 
  what version is currently installed
--Corrected "'xxx' is not a valid DC" error, caused by a lowercase DC identifier in the registry
--installer now captures the current user context and logs it
--added "smart" patching; any and all *.msp files in the same dir as the msi will be automatically applied
--Corrected an error in the InstallSCOMCert utility caused by trying to remove a cert that was not found
--Removed RBA START/END tags from Cert Installer output, if it was called from the Agent Installer


Changes/fixes in Release v1.2.9
-- Not released 1.3.0 uses SCOM 2012 R2 Agent (MMA)


Changes/fixes in Release v1.2.8
--Updated InstallSCOMCert, adding Windows Server 2012 R2 as a supported OS


Changes/fixes in Release v1.2.7
--Added logic to handle unexpected exceptions.  exeptions will be displayed in the RBA output string, avoiding the false
  "connection failed" errors from RBA

  
Changes/fixes in Release v1.2.6
--Added logic to handle timeouts when executing external process, such as InstallSCOMCert.exe or MOMCertImport.exe.


Changes/fixes in Release v1.2.5
--Updated validation routines to throw an error if the DC key in the Rackspace registry is empty/blank
--Updated validation routines to include Windows Server 2012 R2 as a valid operating system
--removed msxml6.msi from the install files, since it should be already installed on most systems
--if /ARIC switch is present, the warning message "SCOM Agent is not installed - nothing to remove" is not displayed.


Changes/fixes in Release v1.2.4
--Corrected the management server for SYD in the config.xml file

Changes/fixes in Release v1.2.3
--Corrected OS Validation to accept Server 2008 RTM with SP2
--changed wording of error message when DNS lookup fails

Changes/Fixes in Release v1.2.2
-- Debug output in InstallSCOMCert was displaying "ERROR:" instead of "DEBUG:"


Changes/Fixes in Release v1.2.1
-- Corrected incorrect behavior /REMOVE, where the installer would attempt to install after removing.
-- Corrected "No Management Group configured" error.  Now making two calls to MSIEXEC to install the agent 
 and the patch, rather than "slipstreaming" both with one call.


Changes/Fixes in Release v1.2.0
-- Updated code and installation files to support installing the SCOM 2012 agent



Changes/Fixes in Release v1.1.5

--#5557 Corrected an issue with getting the Datacenter value from the registry and the value is more than 3 characters long(DFW1, LON3, etc)
--#5750 Corrected an issue where the RemoveCert() function tries to remove a cert even if it does not exist.
--#5751 Added a banner with the version number at the top of the log file to aid in debugging issues
--#5903 Changed the conversion of the OS version to number, forcing a dot to be used as a decimal separator regardless of the culture/language settings



Changes/Fixes in Release v1.1.4

-- #5547 When /LOG is specified, the log files are created but are sometimes empty;  This is most likely the  result of the RBA/ARIC process failing to connect/execute the script properly.  But the issue has been difficult to duplicate.  To help with troubleshooting the issue, I added a test to see if the file exists, if so, the file is opened, clearing the contents and a msg is written to the logfile indicating that the previous contents were deleted.

Added a Flush() after every write ensuring some sort of trail will be left behind in the logfile in the event of a program crash.

-- #5548 Corrected an issue where the DC/Account was not being discovered correctly on 64-bit OS.
The code to look up the DC in the registry was calling an obsolete function that I failed to remove when I wrote the new registry lookup routine. On top of that the registry key path was incorrect for the WOW6423Node  it was looking in HKEYLOCALMACHINE\WOW6432Node\Software\Rackspace when it should have been looking in HKEYLOCALMACHINE\Software\WOW6432Node\Rackspace.

The obsolete function has been removed and the registry path corrected



Changes/Fixes in Release v1.1.3

-- #5113 Added a /LOG option, which will always verbose output to a log file.  Verbose output is sent to the log even if the /V option is not present.

-- #5494  Updated the Usage help text to include documentation on the /LOG option

-- #5495 Detect Customer SCOM environment.  If the SCOM Agent is already installed and it is associated with a non-Rackspace SCOM environment, the installer will exit with an Error message.  The SCOM agent must be installed manually, using the MOMAGENT.MSI installer provided by Microsoft.

-- #5496 Corrected an issue where the installer fails if the /REMOVE option is specified and the agent is not already installed.

-- #5497 /ARIC option now attempts to remove the agent, if it exists.  This is mostly to mitigate VM's that are cloned and the SCOM Agent is not removed and re-installed as part of the cloning process.  The Virt team is working to incorporate the removal the agent during the cloning process.




Changes/Fixes in Release v1.1.0

-- #5140 - Added a /LOG argument.  This will write verbose output to log files(InstallSCOMAgent.log and InstallSCOMCert.log).  This will allow the installers to be run without the /V argument(minimizing screen output) but still have the "verbose" output available for troubleshooting if the installers fail.


-- #5190 - Improved Certificate validation.  If the name of the cert does not match the FQDN of the server or if the cert has expired, the cert is removed and a new one is generated and installed.


-- #5197 - Clarified the documentation concerning the /DC argument



Changes/Fixes in Release v1.0.1

-- #5115 - When executing the installer from a directory different from where the exe is located, the certificate file is not found.  	Changed the code to look in the directory that the EXE is running from.

-- #5116 - If the 1st argument on the command line does not begin with a /, it does not throw a "bad argument" error when it should.  For example, InstallSCOMAgent dfw   should throw an error, indicating the "dfw" is a bad argument; the correct argument should be "/dc dfw".
Corrected the argument validation logic

-- #5141 - config file not found in InstallSCOMCert.  
	Changed the code to look in the directory that the EXE is running from